Release 10.1A: OpenEdge Data Management:
DataServer for ORACLE

Configuring the Progress Explorer administration framework on UNIX

On UNIX, you configure the Progress Explorer administration framework by editing the $DLC/properties/ubroker.properties file. In this file, you provide configuration information for the AppServer, WebSpeed, and DataServers. For general information on how to work with the ubroker.properties file, see OpenEdge Getting Started: Installation and Configuration .

When you configure the OpenEdge DataServer for ORACLE, you are providing information that the Explorer administration framework can use to make sure that it is running the correct DataServer broker instance, that the broker is spawning the appropriate DataServer process, and that broker and servers are running in the correct environment.

Table 5–5 describes the sections in the ubroker.properties file that apply to the OpenEdge DataServer for ORACLE. The file configures a default broker, orabroker1, which you can use as is or use as a template for your own configuration specifications.

Table 5–5: OpenEdge DataServer for ORACLE sections 

Section	Description
[UBroker.OR]	Parent entity of the OpenEdge DataServer for ORACLE brokers. It defines default property settings for all OpenEdge DataServer for ORACLE Broker instances.
[UBroker.OR.orabroker1]	Sample property entity of an OpenEdge DataServer for ORACLE Broker instance. It defines property settings for the OpenEdge DataServer for ORACLE Broker named orabroker1. Note that although many of the settings in this section might work in your environment, some of the settings are for demonstration purposes only. You must specify the appropriate settings for: srvrExecFile — Specify the pathname of DataServer executable you want to use. The default is $DLC/bin/_orasrv. srvrStartupParam — Do not modify the parameters in this section. Note th at the values assigned to the parameters are for the broker’s internal use only. For example, the values of the code-page parameters do not correspond to the values that your client connection might require. You can add startup parameters, however.
[Environment.orabroker1]	Environment settings that apply to the DataServer for ORACLE Broker named orabroker1. Be sure to set the variables to the appropriate values; the values in the file are for demonstration purposes only. ORACLE_HOME and ORACLE_SID are required. Add any environment variables that you want to apply to the DataServer’s environment to this section.

Here are the OpenEdge DataServer for ORACLE sections in the ubroker.properties file:

# # Default properties for broker instances serving Oracle DataServers # # # Default properties for broker instances serving Oracle DataServers # [UBroker.OR] srvrExecFile=$DLC/bin/_orasrv srvrStartupParam=-svub -S X -N TCP -U X -P X -hs 0 -s 40 operatingMode=State-aware classMain=com.progress.ubroker.broker.ubroker portNumber=4445 defaultService=0 initialSrvrInstance=0 minSrvrInstance=0 maxSrvrInstance=256 brkrLoggingLevel=3 description=Oracle DataServer Broker # # Sample Oracle DataServer Broker definition # [UBroker.OR.orabroker1] srvrExecFile=$DLC/bin/_orasrv srvrStartupParam=-svub -S X -N TCP -U X -P X -hs 0 -s 40 srvrLogFile=$WRKDIR/orabroker1.server.log brokerLogFile=$WRKDIR/orabroker1.broker.log portNumber=4445 defaultService=1 appserviceNameList=orabroker1 controllingNameServer=NS1 environment=orabroker1 uuid=172.18.103.53:1f415c:d6330e5d24:-7f4d description=A sample Oracle DataServer Broker # # Environment for Oracle Dataserver Broker: orabroker1 # # Connection to an Oracle database through the Progress # dataserver requires that environment variables for # ORACLE_HOME and ORACLE_SID are set in the context of # a running dataserver broker instance. These values # must either be set in the shell from which the Admin # Service is started or they must be explicitly set here # for the broker instance. # [Environment.orabroker1] # ORACLE_HOME=/u01/oracle/client # ORACLE_SID=ORCL

For a complete description of the parameters included in each of these sections, see the comments in the $DLC/properties/ubroker.properties file. Be sure to preserve the original $DLC/properties/ubroker.properties file. Work with a copy of the file. You must name the copy of the file ubroker.properties. After creating your own version of ubroker.properties, you can verify its settings by using the oraconfig utility. See Appendix E, "DataServer Command Line Utilities and Startup Parameters," for more information.

The ubroker.properties file is read on startup of the AdminServer process. For changes in any used environment variables to take effect, you must restart the AdminServer.

Validating ubroker.properties content

Whenever you create your own version of the ubroker.properties file, you should use the relevant validation utility to validate your changes and make sure that there are no syntax errors or conflicts. When configuring the DataServer for ORACLE, you validate the file by using the oraconfig utility. For information about the ORACONFIG utility, see Appendix E, "DataServer Command Line Utilities and Startup Parameters," for more information.

Configuring multiple brokers

You can configure multiple brokers by adding more [UBroker.OR.broker-name] and [Environment.broker-name] sections. Each broker instance must have a unique name. The brokers can share the properties that you define in the parent entity [UBroker.OR] section.

If you want to access multiple ORACLE databases, you must configure one broker per database, and each broker must run in a separate directory and a distinct environment. For example, each broker must have a unique setting for ORACLE_SID.

Using the NameServer

By default, your DataServer for ORACLE broker instances are defined with a controlling NameServer and are provided with a default Data Service. Progress Software Corporation recommends using a NameServer configuration at all times. In such cases, the DataServer client’s initial connection is to the NameServer. However, you can alternatively connect the DataServer directly to the broker instance by setting the -DataService value to none in the connection parameters of your schema holder. If you will always use a -DataService value of none, you should remove the controlling NameServer from your broker instance definition. See OpenEdge Getting Started: Installation and Configuration for more information about the NameServer’s role in a configuration.

Note: Do not simultaneously run some DataServers for ORACLE under brokers with controlling NameServers and others directly under brokers (that is, without controlling NameServers). This defeats the purpose of using a NameServer to control brokers. If you do this, the benefits of the NameServer are lost and load balancing is ineffective. Progress Software Corporation recommends that you always use a NameServer, with one exception: you can choose initially to connect directly to a broker to simplify confirming an initial connection. Once you establish a connection, Progress Software Corporation recommends that you reintroduce the NameServer into your configuration.